EMBEDDED UNIVERSAL INTEGRATED CIRCUIT CARD (eUICC) FILE SYSTEM MANAGEMENT WITH PROFILE SWITCHING

ABSTRACT

Methods and apparatus for dynamic file system management of an embedded Universal Integrated Circuit Card (eUICC) in response to changes for electronic Subscriber Identity Modules (eSIMs) on the eUICC are disclosed herein. Hardware specific file information, e.g., hardware-based eUICC parameters, which may apply to multiple eSIMs and/or multiple Mobile Network Operators (MNOs), is included in a default eUICC file system. MNO specific information, e.g., MNO-specified parameters, is included in eSIMs. Customized eUICC level files are created, stored, modified and/or replaced based on a combination of default eUICC files and MNO specific information extracted from an eSIM at installation and/or in response to a change of state of the eSIM, such as when enabling, disabling, or updating the eSIM on the eUICC.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/252,119, entitled “EMBEDDED UNIVERSAL INTEGRATED CIRCUIT CARD (eUICC)FILE SYSTEM MANAGEMENT WITH PROFILE SWITCHING,” filed Jan. 18, 2019, setto issue Jun. 2, 2020 as U.S. Pat. No. 10,674,352, which is acontinuation of U.S. patent application Ser. No. 15/366,737, entitled“EMBEDDED UNIVERSAL INTEGRATED CIRCUIT CARD (eUICC) FILE SYSTEMMANAGEMENT WITH PROFILE SWITCHING,” filed Dec. 1, 2016, issued Jan. 22,2019 as U.S. Pat. No. 10,187,788, which claims the benefit of U.S.Provisional Patent Application No. 62/266,464, entitled “EMBEDDEDUNIVERSAL INTEGRATED CIRCUIT CARD (eUICC) FILE SYSTEM MANAGEMENT WITHPROFILE SWITCHING” filed Dec. 11, 2015, the contents of all of which areincorporated by reference herein in their entireties for all purposes.

FIELD

The described embodiments set forth various techniques for embeddedUniversal Integrated Circuit Card (eUICC) file system management withelectronic Subscriber Identity Module (eSIM) profile switching.

BACKGROUND

Most mobile devices are configured to receive and operate removableUniversal Integrated Circuit Cards (UICCs) that enable the mobiledevices to access services provided by wireless service providers, whichcan include mobile network operators (MNOs) and virtual MNOs (VMNOs). Inparticular, each UICC includes at least a microprocessor and a read-onlymemory (ROM), where the ROM is configured to store different applets andauthentication data that the mobile device can use to register andaccess services of the wireless service providers. Typically, a UICCtakes the form of a small removable card (e.g., a SIM card) that isconfigured to store a single MNO profile and to be inserted into aUICC-receiving bay included in the mobile device. In more recentimplementations, however, UICCs are being embedded directly into systemboards of mobile devices and are configured to store one or more MNOprofiles (e.g., electronic SIMs (eSIMs))—e.g., one eSIM (profile) for alocal MNO, and another eSIM (profile) for an international MNO. Notably,these embedded UICCs (eUICCs) provide several advantages overtraditional, removable UICCs. For example, some eUICCs include arewritable memory that can facilitate eSIM addition, deletion, andupdating for accessing new and/or different services provided by MNOs.EUICCs can also eliminate the necessity of including UICC-receiving bayswithin mobile devices. The implementation of eUICCs therefore not onlyincreases the flexibility of mobile devices, but also simplifies theirdesign and frees up space for other components.

Despite the foregoing advantages provided by eUICCs, new challengesarise with respect to maintaining backward compatibility with externalprocessing modules designed to work with file systems as installed onand structured for UICCs, while also providing the increased flexibilityoffered by eUICCs, particularly with eSIM (profile) switching thatimpacts the file systems installed on eUICCs. Legacy file systems forlegacy UICCs can mix MNO specific information with hardware specific(e.g., UICC based) information. File system management for eUICCs, onwhich eSIM profiles can be added, deleted, and/or modified, can beimproved to allow for flexible eSIM profile management as well as retainbackward compatibility with external processing modules, e.g., aterminal interface, that are also designed to work with legacy UICCs.

SUMMARY

Representative embodiments set forth herein disclose various techniquesfor dynamically organizing and managing file systems on an embeddedUniversal Integrated Circuit Card (eUICC) in response to electronicSubscriber Identity Module (eSIM) changes on the eUICC. Hardwarespecific file information, e.g., hardware-based eUICC parameters, whichmay apply to multiple eSIMs and/or to multiple MNOs, is included in adefault eUICC file system. Mobile Network Operator (MNO) specificinformation, e.g., MNO-specified parameters, is included in individualeSIMs associated with corresponding MNOs. Customized eUICC level filesare created, stored, modified, and/or replaced on the eUICC based atleast in part on combining information from one or more default eUICCfiles and MNO specific information extracted from one or more eSIMs atinstallation and/or in response to a change of state of the one or moreeSIMs, such as when enabling, disabling, or updating the one or moreeSIMs on the eUICC.

A representative embodiment sets forth a method for file systemmanagement of an eUICC for an eSIM associated with an MNO. Specifically,the method is implemented at the eUICC that stores the eSIM, andincludes: receiving an eSIM to be stored within the eUICC; storing theeSIM within the eUICC; parsing a file system of the eSIM to identify MNOspecific information applicable to an eUICC level file; and updating theeUICC level file based at least in part on the MNO specific information.

Another representative embodiment sets forth a method for file systemmanagement of an eUICC for an eSIM associated with an MNO. Specifically,the method is implemented at the eUICC that stores the eSIM, andincludes: obtaining an eSIM to be enabled within the eUICC; identifyingMNO specific information in the eSIM; constructing at least onecustomized eUICC level file based on the MNO specific information;storing the at least one customized eUICC level file in the eUICC forfuture use; and updating corresponding eUICC level files based on the atleast one customized eUICC level file, in response to receipt of anindication to enable the eSIM on the eUICC.

This Summary is provided merely for purposes of summarizing some exampleembodiments so as to provide a basic understanding of some aspects ofthe subject matter described herein. Accordingly, it will be appreciatedthat the above-described features are merely examples and should not beconstrued to narrow the scope or spirit of the subject matter describedherein in any way. Other features, aspects, and advantages of thesubject matter described herein will become apparent from the followingDetailed Description, Figures, and Claims.

Other aspects and advantages of the embodiments described herein willbecome apparent from the following detailed description taken inconjunction with the accompanying drawings which illustrate, by way ofexample, the principles of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only toprovide examples of possible structures and arrangements for thedisclosed inventive apparatuses and methods for providing wirelesscomputing devices. These drawings in no way limit any changes in formand detail that may be made to the embodiments by one skilled in the artwithout departing from the spirit and scope of the embodiments. Theembodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings, wherein likereference numerals designate like structural elements.

FIG. 1 illustrates a block diagram of different exemplary components ofa system configured to implement the various techniques describedherein, according to some embodiments.

FIG. 2 illustrates a block diagram of a more detailed view of particularcomponents of the system of FIG. 1, according to some embodiments.

FIG. 3 illustrates a block diagram of an exemplary eUICC file systemthat can be implemented to manage eSIM profiles in the eUICC, accordingto some embodiments.

FIG. 4 illustrates an example method for file system management of theeUICC file system based on a received eSIM profile, according to someembodiments.

FIG. 5 illustrates a flow diagram for merging hardware specificinformation with MNO specific information to update an eUICC file systembased on an eSIM profile, according to some embodiments.

FIG. 6 illustrates another example method for file system management ofthe eUICC file system based on an obtained eSIM profile, according tosome embodiments.

FIG. 7 illustrates a detailed view of an exemplary computing device thatcan be used to implement the various apparatuses and methods describedherein, according to some embodiments.

DETAILED DESCRIPTION

Representative applications of apparatuses and methods according to thepresently described embodiments are provided in this section. Theseexamples are being provided solely to add context and aid in theunderstanding of the described embodiments. It will thus be apparent toone skilled in the art that the presently described embodiments can bepracticed without some or all of these specific details. In otherinstances, well known process steps have not been described in detail inorder to avoid unnecessarily obscuring the presently describedembodiments. Other applications are possible, such that the followingexamples should not be taken as limiting.

In accordance with various embodiments described herein, the terms“wireless communication device,” “wireless device,” “mobile device,”“mobile station,” and “user equipment” (UE) may be used interchangeablyherein to describe one or more common consumer electronic devices thatmay be capable of performing procedures associated with variousembodiments of the disclosure. In accordance with variousimplementations, any one of these consumer electronic devices may relateto: a cellular phone or a smart phone, a tablet computer, a laptopcomputer, a notebook computer, a personal computer, a netbook computer,a media player device, an electronic book device, a MiFi® device, awearable computing device, as well as any other type of electroniccomputing device having wireless communication capability that caninclude communication via one or more wireless communication protocolssuch as used for communication on: a wireless wide area network (WWAN),a wireless metro area network (WMAN) a wireless local area network(WLAN), a wireless personal area network (WPAN), a near fieldcommunication (NFC), a cellular wireless network, a fourth generation(4G) LTE, LTE Advanced (LTE-A), and/or 5G or other present or futuredeveloped advanced cellular wireless networks.

The wireless communication device, in some embodiments, can also operateas part of a wireless communication system, which can include a set ofclient devices, which can also be referred to as stations, clientwireless devices, or client wireless communication devices,interconnected to an access point (AP), e.g., as part of a WLAN, and/orto each other, e.g., as part of a WPAN and/or an “ad hoc” wirelessnetwork. In some embodiments, the client device can be any wirelesscommunication device that is capable of communicating via a WLANtechnology, e.g., in accordance with a wireless local area networkcommunication protocol. In some embodiments, the WLAN technology caninclude a Wi-Fi (or more generically a WLAN) wireless communicationsubsystem or radio, the Wi-Fi radio can implement an Institute ofElectrical and Electronics Engineers (IEEE) 802.11 technology, such asone or more of: IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or otherpresent or future developed IEEE 802.11 technologies.

Additionally, it should be understood that the UEs described herein maybe configured as multi-mode wireless communication devices that are alsocapable of communicating via different third generation (3G) and/orsecond generation (2G) RATs. In these scenarios, a multi-mode UE can beconfigured to prefer attachment to LTE networks offering faster datarate throughput, as compared to other 3G legacy networks offering lowerdata rate throughputs. For instance, in some implementations, amulti-mode UE may be configured to fall back to a 3G legacy network,e.g., an Evolved High Speed Packet Access (HSPA+) network or a CodeDivision Multiple Access (CDMA) 2000 Evolution-Data Only (EV-DO)network, when LTE and LTE-A networks are otherwise unavailable.

A traditional, removable Universal Integrated Circuit Card (UICC)maintains a minimal file system (FS) with which to perform, at least inpart, an initialization procedure for the UICC. Wireless serviceproviders, such as a Mobile Network Operator (MNO), control access totheir wireless services by distributing to subscribers customized UICCs,which may include pre-installed Subscriber Identity Module (SIM)profiles. The UICCs can be manufactured and customized according to theMNO's specifications. The FS of traditional, legacy UICCs includes filesthat may combine hardware specific information (e.g., parametersappropriate for the specific UICC) and MNO specific information (e.g.,MNO specified parameters, and/or one or more SIM profiles for the MNO).With newer non-removable embedded UICCs (eUICCs) installed directly inmobile devices, MNO specific information can be added to the eUICCseparately from manufacture and/or initialization of the eUICC and/orthe mobile device. For example, SIM profiles and/or UICC softwaremodules in a mobile device can be customized during distribution(post-manufacture), at a time of sale, and/or after delivery to a user.A single mobile device with an eUICC can be customized to work with oneor more different MNOs, and as such, MNO specific information should beseparable from eUICC (hardware-specific) information when possible.Furthermore, as eSIM profiles can be enabled and/or disabled undersoftware control, the eUICC of a mobile device can exist in a state inwhich no eSIM profile is enabled on the eUICC. Legacy UICC files thatinclude both hardware information and MNO specific information can beunable to be defined by an MNO for use in a mobile device that includesan eUICC, as the MNO eSIM can be installed and/or enabled in differentmobile devices that include eUICCs from different manufacturers and/orversions. An MNO may seek to manage MNO specific parameters that applyto a broad variety of eUICCs manufactured for different mobile devicesoffered by different product manufacturers. A product manufacturer mayalso seek to manage hardware specific parameters independent of MNOspecific requirements. As such, a dynamically customizable file systemfor the eUICC can provide flexibility in adapting various eUICC levelfiles as eSIMs from different MNOs are installed, enabled, disabled,and/or modified.

A default eUICC file system can be dynamically updated based on eSIMprofiles installed and/or enabled on the eUICC. The default eUICC filesystem can include a limited number of files stored at the eUICC level,e.g., directly at or below a master file (MF) level in the eUICC. Thedefault eUICC file system can be available when no eSIMs are installedand/or enabled on the eUICC. The default eUICC file system can providelimited functionality for communication between the eUICC and externalprocessing modules, such as with a terminal module executing on anapplications processor communicatively coupled with the eUICC. A numberof eUICC files in the default eUICC file system can include hardwarespecific parameters and/or configurations. Some initial communicationprocedures, e.g., as specified in ETSI TS 102 221, entitled “SmartCards—UICC-Terminal Interface Physical and Logical Characteristics”, andincorporated by reference herein in its entirety for all purposes,include requirements for a basic file system. For example, the basicfile system for a UICC (and consequently also for an eUICC) includes aMaster File (MF). Initialization of the UICC (and eUICC) can include anexchange of terminal communication capabilities after selection of anMF. Similarly, wireless circuitry, e.g., a baseband component, canexpect a number of basic files to exist, such as an elementary file (EF)of a directory (DIR) type, an EF of an ICC Identifier (ICCID) type, aUniversal SIM (USIM), or a combination of these, without which thebaseband component may report an error. As described further herein, aset of eUICC level files can be included as a default file system forthe eUICC and include sufficient information for initialization of theeUICC and communication with processing circuitry external to the eUICC.The default file system can be available even when no eSIMs areinstalled and/or enabled. The default file system can be updated and/ordynamically customized based on MNO specific information available fromeSIMs when installed, enabled, disabled, and/or modified.

In some embodiments, a file system of an eUICC is updated based onchanges to one or more eSIMs on the eUICC. Contents of certain files,particularly files at the eUICC level, can be updated and/or replacedwith new files when changing eSIMs. For example the Master File (MF) fora default file system can be replaced with a customized MF based on MNOspecific parameters extracted from (and/or derived from information in)one or more eSIMs. When an eSIM is enabled, disabled, and/or modifiedone or more files of the eUICC file system can be updated and/orreplaced. In some embodiments, when an eSIM is installed on the eUICC, afile system image can be constructed based on information extracted from(and/or based on information available in) the eSIM, and the file systemimage can be stored in the eUICC for later use when the eSIM is enabled.Thus, real-time merging of files can be avoided by preparing customizedfile system images (and/or portions thereof, such as particular files ofa file system) in advance. In some embodiments, when an eSIM is disabledon the eUICC, a previous file system image and/or a default file systemimage can replace the file system in use.

A more detailed discussion is provided below and described inconjunction with FIG. 1 to FIG. 7, which illustrate detailed diagrams ofdifferent systems and methods that can be used to implement thesetechniques.

FIG. 1 illustrates a block diagram of different components of a system100 that is configured to implement the various techniques describedherein, according to some embodiments. More specifically, FIG. 1illustrates a high-level overview of the system 100, which, as shown,includes a mobile device 102, one or more base stations 112, and one ormore MNOs 114. According to one embodiment, the mobile device 102represents a wireless communication device (e.g., a smart phone, atablet, a laptop, etc.) that is configured (and/or configurable) tocommunicate with at least one of the MNOs 114 via at least one of thebase stations 112. As shown in FIG. 1, the mobile device 102 can includea processor 104, a memory 106, an eUICC 108, and a baseband component110. The eUICC 108 can represent, for example, a hardware component thatis embedded within a system board of the mobile device 102 and isconfigured to provide a more flexible environment than traditional,removable UICCs (e.g., SIM cards). As described in greater detail below,the eUICC 108 can include a variety of hardware and software componentsthat enable the eUICC 108 to manage one or more file systems on theeUICC in conjunction with changes to eSIMs on the eUICC 108, accordingto the techniques described herein. Although not illustrated in FIG. 1,the mobile device 102 can also be configured to include a receiving bayfor a removable UICC (e.g., a SIM card), on which a file system for theUICC can likewise be managed dynamically as one or more eSIMs arechanged on the UICC in a similar manner using the techniques describedherein.

FIG. 2 illustrates a block diagram of a more detailed view 200 ofparticular components of the mobile device 102 of FIG. 1, according tosome embodiments. As shown in FIG. 2, the processor 104, in conjunctionwith the memory 106, can implement a main operating system (OS) 202 thatis configured to execute applications 204 (e.g., native OS applicationsand user applications). As also shown in FIG. 2, the eUICC 108 can beconfigured to implement an eUICC OS 206 that is configured to manage thehardware resources of the eUICC 108 (e.g., a processor and a memoryembedded in the eUICC 108). The eUICC OS 206 can also be configured tomanage eSIMs 208 that are stored by the eUICC 108, e.g., by activating,deactivating, modifying, or otherwise performing management of the eSIMs208 within the eUICC 108 and providing the baseband component 110 withaccess to the eSIMs 208 to provide access to wireless services for themobile device 102. The eUICC 108 OS can also perform file systemmanagement for eUICC 108 level files and update certain eUICC 108 levelfiles based on changes in status and/or installation and/or removal ofeSIMs 208 on the eUICC 108. The eUICC 108 OS can include an eSIM manager210, which in some embodiments can be an Issue Security Domain (ISD)level application, a “security domain” in accordance with aGlobalPlatform specification, a security domain associated with one ormore eSIMs and that calls additional eUICC OS installation services,and/or an application that implements a specific set of securityservices, e.g., for establishing and managing a secure channel and/or toprovide encryption/decryption functions. The eSIM manager 210 canperform management functions for various eSIMs 208. According to theillustration shown in FIG. 2, each eSIM 208 can include a number ofapplets 212 that define the manner in which the eSIM 208 operates. Forexample, one or more of the applets 212, when implemented by thebaseband component 110 and the eUICC 108, can be configured to enablethe mobile device 102 to communicate with an MNO 114 and provide usefulfeatures (e.g., phone calls and internet) to a user of the mobile device102.

As also shown in FIG. 2, the baseband component 110 of the mobile device102 can include a baseband OS 214 that is configured to manage hardwareresources of the baseband component 110 (e.g., a processor, a memory,different radio components, etc.). According to some embodiments, thebaseband component 110 can implement a manager 216 that is configured tointerface with the eUICC 108 to implement various techniques describedherein, which can include establishing a secure channel with aprovisioning server 116 and obtaining information (such as eSIM 208data) from the provisioning server 116 for purposes of managing eSIMs208, including but not limited to provisioning, loading, installing,adding, modifying, updating, deleting, enabling, disabling, orperforming other management operations for one or more eSIMs 208. Asalso shown in FIG. 2, the manager 216 can be configured to implementservices 218, which represents a collection of software modules that areinstantiated by way of the various applets 212 of enabled eSIMs 208 thatare included in the eUICC 108. For example, services 218 can beconfigured to manage different connections between the mobile device 102and MNOs 114 according to the different eSIMs 208 that are enabledwithin the eUICC 108.

FIG. 3 illustrates a block diagram 300 of an eUICC 108 file system thatcan be implemented to manage eSIMs 208 (also referred to herein asprofiles and/or as eSIM 208 profiles) in the eUICC 108, according tosome embodiments. A limited number of basic files can be stored at theeUICC 108 level of the eUICC 108 and made available independent ofwhether any eSIMs 208 are installed and/or enabled. External processorsof a mobile device 102 in which the eUICC 108 resides, such as processor104 of the mobile device 102 show in FIGS. 1 and 2 can communicate withthe eUICC 108 via a terminal module that expects certain files to beinitialized and functional in order for the eUICC 108 to operateproperly (e.g., in accordance with standardized UICC terminal interfacerequirements.) Within an eUICC memory 302 of the eUICC 108, the basicfiles of the eUICC 108 file system can include a Master File (MF) 304,which is related to a set of additional eUICC 108 level elementary files(EFs). The eUICC 108 level EFs can include an elementary file EF_(UMPC)306, an elementary file EF_(EVN_CLASSES) 308, and an elementary fileEF_(DIR) 310. The elementary file EF_(UMPC) 306 specifies a number ofhardware specific operating parameters, e.g., a UICC maximum powerconsumption (UMPC) and a UICC increased idle current value. Within alegacy UICC, the elementary file EF_(UMPC) 306 can also include MNOdefined parameters, such as an MNO defined time-out value that indicatesa minimum time delay value for execution of commands by the UICC whenexternal processing circuitry provides less than the allowed UICCmaximum current level. Similarly, in an eUICC 108, such MNO definedtime-out values can be required when using an eSIM 208 associated withan MNO. When provisioning the eUICC 108 initially, or in a defaultconfiguration, e.g., when no eSIMs 208 are enabled and/or installed, theeUICC 108 level file system can include a basic set of files thatprovide minimal functionality. The eUICC 108 level files can be updated,e.g., additional MNO specific information extracted from an eSIM 208 andmerged with hardware specific information already resident (and/orupdated based on the MNO specific information) in the eUICC 108 levelfiles. For example, the elementary file EF_(UMPC) 306 can be updated toinclude MNO defined parameters from an eSIM 208 when the eSIM 208 isinstalled and/or enabled. By separating MNO specific information fromhardware-based information, an MNO can supply an eSIM 208 profile thatapplies to different eUICC 108 hardware configurations and/or fordifferent mobile devices 102 and/or for different eUICC 108manufacturers and/or for different mobile device 102manufacturers/distributors/vendors. Hardware platform based parametersspecific to the eUICC 108 hardware can be separated from serviceprovider, e.g., mobile network operator (MNO), based parameters.Additional basic eUICC 108 level files can include hardware specificinformation that can be used with any combination of enabled/installedeSIMs 208. The elementary file EF_(EVN_CLASSES) 308 specifies hardwareparameters for the eUICC 108 for different environment classes. Theelementary file EF_(DIR) 310 provides a directory of application files,such as eSIM 208 profiles resident on the eUICC 108. The eUICC 108 caninclude multiple eSIM 208 profiles, e.g., eSIM₁ 208-1 through eSIM_(N)208-N, which each can be configured in different states. When an eSIM208 is installed and/or enabled, information specific to an MNOassociated with the eSIM 208 can be merged into one or more of the eUICC108 level files to update the file system based on the set of eSIMs 208enabled on the eUICC 108. Similarly, when an eSIM 208 is modified, anyinformation relevant to the eUICC 108 level files can also be updated.Furthermore, when an eSIM 208 is disabled, the eUICC 108 level files canbe updated to remove (or otherwise mark as inactive) the MNO specificinformation for the disabled eSIM 208 when no longer required. In someembodiments, when multiple eSIMs 208 are associated with the same MNOand/or use the same MNO specific parameters for one or more of the eUICC108 level files, minimal or no updating of the eUICC 108 level files maybe needed except when changing between a state when no eSIMs 208 areenabled for an associated MNO and a state when at least one eSIM 208 isenabled for the associated MNO.

FIG. 4 illustrates a flowchart 400 for a representative method for filesystem management of an eUICC 108 file system based on a received eSIM208 profile, according to some embodiments. At 402, the eUICC 108 of amobile device 102 can receive an eSIM 208 profile, and at 404, the eUICC108 can store the eSIM 208 profile within the eUICC 108. At 406, theeUICC 108 can parse a file system of the eSIM 208 profile to identifyMNO specific information applicable to an eUICC 108 level file. In someembodiments, the MNO specific information can apply to multiple eUICC108 level files. At 408, the eUICC 108 can update the eUICC 108 levelfile based on the MNO specific information identified in the eSIM 208profile. In some embodiments, one or more eUICC 108 level files can becreated by merging MNO specific information (and/or based on such MNOspecific information) extracted from the eSIM 208 profile with one ormore generic (or previously modified) eUICC 108 level files. The updatedeUICC 108 level files created by the merging can be stored in the eUICC108 to be ready for use if and when the eSIM 208 profile is enabled. Insome embodiments, the updated eUICC 108 level files replace currentversions of corresponding eUICC 108 level files when the eSIM 208profile is enabled. In some embodiments, the previous versions of eUICC108 level files are stored for backup and/or to allow for reversion toprevious versions of eUICC 108 level files, e.g., when disabling theeSIM 208 profile and/or when removing the eSIM 208 profile. In someembodiments, a default version of one or more eUICC 108 level files arestored in the eUICC 108, e.g., for use when no eSIM 208 profiles areenabled and/or installed on the eUICC 108. In some embodiments, pastversions (other than default versions) of one or more eUICC 108 levelfiles are not stored in the eUICC 108, and new versions of the one ormore eUICC 108 level files are created, as required, based at least inpart on eSIM 208 installation, enabling, disabling, modifying, updating,removing, or other applicable eSIM 208 profile management functions.

FIG. 5 illustrates a flow diagram 500 for merging hardware specificinformation (such as for an eUICC 108) and MNO specific information(e.g., from an eSIM 208 profile) to update an eUICC 108 file systembased on the eSIM 208 profile, according to some embodiments. A default(or present version) eUICC 108 level file, e.g., elementary fileEF_(UMPC) 306 can contain eUICC generic information 504 (relevant to theeUICC 108). Additional information associated with an MNO can beextracted from an MNO provided file, e.g., from the eSIM 208 profile.The additional MNO specific information can apply to one or moredifferent eUICC 108 level files. For example, the eSIM 208 profile cancontain MNO specific information 506 applicable to an elementary file,such as to elementary file EF_(UMPC) 306 as shown in FIG. 3 or toelementary file EF_(UMPC) 502 as shown in FIG. 5. The eUICC genericinformation 504 can be merged by the eUICC OS 206 with the MNO specificinformation 506 to create an updated eUICC 108 level file, e.g., anupdated elementary file EF_(UMPC) 508. In some embodiments, the updatedelementary file EF_(UMPC) 508 is created when the eSIM 208 profile isinstalled on the eUICC 108 and stored in the eUICC 108 for use when theeSIM 208 profile is enabled, e.g., to separate the process of merginginformation from eSIM 208 profiles from enabling of eSIMs 208. In someembodiments, the updated elementary file EF_(UMPC) 508 is created inreal-time when the eSIM 208 is enabled based at least in part on apresently in use eUICC 108 elementary file EF_(UMPC) 502 and on MNOspecific information 506 extracted from the eSIM 208 profile. In someembodiments, such as when only one eSIM 208 profile is enabled at atime, when switching between eSIM 208 profiles, corresponding elementaryfiles EF_(UMPC) 508 for the eSIM 208 can be already stored, e.g., wheneach eSIM 208 is installed, corresponding elementary files that becustomized with information extracted from the eSIM 208, such aselementary file EF_(UMPC) 508, can be created and stored in the eUICC108 and available for immediate use when enabling an eSIM 208 profile.Thus, switching between eSIM 208 profiles can be aided by switchingbetween different sets of eUICC 108 level elementary files whenswitching eSIM 208 profiles. When more than one eSIM 208 profile can beenabled simultaneously in the eUICC 108, one or more updated eUICC 108level elementary files can be created when applicable elementary filesbased on the combination of eSIM 208 profiles that will be enabled arenot pre-stored on the eUICC 108.

FIG. 6 illustrates a flowchart 600 for another exemplary method for filesystem management of an eUICC 108 level file system based on an obtainedeSIM 208 profile, according to some embodiments. At 602, the eUICC 108obtains an eSIM 208 profile to be enabled within the eUICC 108. In someembodiments, the eSIM 208 profile is stored in the eUICC 108 for futureuse, e.g., not enabled when installed. In some embodiments, the eSIM 208profile is stored in the eUICC 108 and also enabled as part ofinstallation of the eSIM 208 profile. In some embodiments, the eUICC 108receives one or more eSIM 208 management commands, e.g., via a terminalinterface from an external processor 104 of the mobile device 102, toenable an eSIM 208 profile already stored in the eUICC 108. At 604, theeUICC 108 identifies MNO specific information in the eSIM 208. In someembodiments, the MNO specific information applies to one or moredifferent eUICC 108 level files. At 606, the eUICC 108 constructs atleast one customized eUICC 108 level file based on the identified MNOspecific information from the eSIM 208 profile. At 608, the eUICC 108stores the at least one customized eUICC 108 level file in the eUICC 108for future use, e.g., when enabling the eSIM 208. At 610, the eUICCupdates corresponding eUICC 108 level files based on the at least onecustomized eUICC 108 level file, in response to receipt of an indicationto enable the eSIM 208. In some embodiments, updating the correspondingeUICC 108 level files includes replacing presently used eUICC 108 levelfiles with one or more of the at least one customized eUICC 108 levelfiles. In some embodiments, updating the corresponding eUICC 108 levelfiles includes modifying parameters for the eUICC 108 level files basedon the stored at least one customized eUICC 108 level files. In someembodiments, customized eUICC 108 level files are dynamically created inresponse to enabling an eSIM 208 profile. In some embodiments,customized eUICC 108 level files are accessed (e.g., from storage in theeUICC 108) when an eSIM 208 profile is enabled, disabled, modified,updated, installed, and/or removed from the eUICC 108.

FIG. 7 illustrates a detailed view of a computing device 700 that can beused to implement the various components described herein, according tosome embodiments. In particular, the detailed view illustrates variouscomponents that can be included in the mobile device 102 illustrated inFIG. 1. As shown in FIG. 7, the computing device 700 can include aprocessor 702 that represents a microprocessor or controller forcontrolling the overall operation of computing device 700. The computingdevice 700 can also include a user input device 708 that allows a userof the computing device 700 to interact with the computing device 700.For example, the user input device 708 can take a variety of forms, suchas a button, keypad, dial, touch screen, audio input interface,visual/image capture input interface, input in the form of sensor data,etc. Still further, the computing device 700 can include a display 710(screen display) that can be controlled by the processor 702 to displayinformation to the user. A data bus 716 can facilitate data transferbetween at least a storage device 740, the processor 702, and acontroller 713. The controller 713 can be used to interface with andcontrol different equipment through and equipment control bus 714. Thecomputing device 700 can also include a network/bus interface 711 thatcouples to a data link 712. In the case of a wireless connection, thenetwork/bus interface 711 can include a wireless transceiver.

The computing device 700 also include the storage device 740, which canrepresent a single storage device or multiple storage devices, andincludes a storage management module that manages one or more partitionswithin the storage device 740. In some embodiments, storage device 740can include solid-state memory or the like. The computing device 700 canalso include a Random Access Memory (RAM) 720 and a Read-Only Memory(ROM) 722. The ROM 722 can store programs, utilities or processes to beexecuted in a non-volatile manner. The RAM 720 can provide volatile datastorage, and stores instructions related to the operation of thedifferent software processes described herein. When the computing device700 represents a mobile device 102, the computing device 700 can furtherinclude a secure element 750 that can represent the eUICC 108illustrated in FIGS. 1 and 2 and described in detail herein.

Representative Embodiments

In some embodiments, a method for file system management on an embeddedUniversal Integrated Circuit Card (eUICC) includes the eUICC: receivinga request to store an electronic Subscriber Identify Module (eSIM)within a memory that is accessible to the eUICC; and in response to therequest: storing the eSIM into the memory, parsing a file system of theeSIM to identify Mobile Network Operator (MNO) specific informationapplicable to an eUICC level file, and updating the eUICC level filebased at least in part on the identified MNO specific information.

In some embodiments, the eUICC is included in a mobile device configuredto access wireless services provided by the MNO while the eSIM isinstalled and enabled on the eUICC. In some embodiments, the memory isincluded within the eUICC. In some embodiments, updating the eUICC levelfile based at least in part on the identified MNO specific informationincludes merging at least part of the MNO specific information with apresent version of the eUICC level file. In some embodiments, the methodfurther includes the eUICC storing the updated eUICC level file in thememory for future use. In some embodiments, the method further includesthe eUICC replacing a present version of the eUICC level file with thestored updated eUICC level file in response to receipt of a command toenable the eSIM. In some embodiments, the eUICC level file includes anelementary file (EF) that includes hardware specific parameters for theeUICC. In some embodiments, the updated eUICC level file includes anelementary file (EF) that includes hardware specific parameters for theeUICC and MNO specific parameters for the eSIM. In some embodiments, theMNO specific information in the eSIM includes an elementary file (EF) ora data object that defines one or more operating parameters for theeUICC and specified by the MNO. In some embodiments, the method furtherincludes the eUICC replacing a present version of the eUICC level filewith a default stored eUICC level file in response to receipt of acommand to disable one or more eSIMs of the eUICC after which no eSIMSwill be enabled on the eUICC.

In some embodiments, an apparatus configurable for operation in a mobiledevice includes a memory and a processor communicatively couple to thememory and configured to cause the apparatus to carry out steps thatinclude: receiving a request to store an electronic Subscriber IdentifyModule (eSIM) within the memory; and in response to the request: storingthe eSIM into the memory, parsing a file system of the eSIM to identifyMobile Network Operator (MNO) specific information applicable to aneUICC level file, and updating the eUICC level file based at least inpart on the identified MNO specific information.

In some embodiments, the apparatus is an embedded Universal IntegratedCircuit Card (eUICC) included in the mobile device. In some embodiments,the mobile device is configured to access wireless services provided bythe MNO while the eSIM is installed and enabled on an eUICC included inthe mobile device. In some embodiments, the memory is included within aneUICC. In some embodiments, updating the eUICC level file based at leastin part on the identified MNO specific information includes merging atleast part of the MNO specific information with a present version of theeUICC level file. In some embodiments, the steps carried out by theapparatus further include storing the updated eUICC level file in thememory for future use. In some embodiments, the steps carried out by theapparatus further include replacing a present version of the eUICC levelfile with the stored updated eUICC level file in response to receipt ofa command to enable the eSIM. In some embodiments, the eUICC level fileincludes an elementary file (EF) that includes hardware specificparameters for an eUICC. In some embodiments, the updated eUICC levelfile includes an elementary file (EF) that includes hardware specificparameters for an eUICC and MNO specific parameters for the eSIM. Insome embodiments, the MNO specific information in the eSIM includes anelementary file (EF) or a data object that defines one or more operatingparameters for an eUICC and specified by the MNO. In some embodiments,the steps carried out by the apparatus further include replacing apresent version of the eUICC level file with a default stored eUICClevel file in response to receipt of a command to disable one or moreeSIMs after which no eSIMs will be enabled for the mobile device. Insome embodiments, the eSIMs are stored in an eUICC of the mobile device.

In some embodiments, a mobile device includes an electronic UniversalIntegrated Circuit Card (eUICC); and a processor configured to cause themobile device to carry out steps that include: receiving a request tostore an electronic Subscriber Identify Module (eSIM) within a memorythat is accessible to the eUICC; and in response to the request: storingthe eSIM into the memory, parsing a file system of the eSIM to identifyMobile Network Operator (MNO) specific information applicable to aneUICC level file, and updating the eUICC level file based at least inpart on the identified MNO specific information.

In some embodiments, the mobile device is configured to access wirelessservices provided by the MNO while the eSIM is installed and enabled onthe eUICC. In some embodiments, the memory is included within the eUICC.In some embodiments, updating the eUICC level file based at least inpart on the identified MNO specific information includes merging atleast part of the MNO specific information with a present version of theeUICC level file. In some embodiments, the steps carried out by themobile device further include storing the updated eUICC level file inthe memory for future use. In some embodiments, the steps carried out bythe mobile device further include replacing a present version of theeUICC level file with the stored updated eUICC level file in response toreceipt of a command to enable the eSIM. In some embodiments, the eUICClevel file includes an elementary file (EF) that includes hardwarespecific parameters for the eUICC. In some embodiments, the updatedeUICC level file includes an elementary file (EF) that includes hardwarespecific parameters for the eUICC and MNO specific parameters for theeSIM. In some embodiments, the MNO specific information in the eSIMincludes an elementary file (EF) or a data object that defines one ormore operating parameters for the eUICC and specified by the MNO. Insome embodiments, the steps carried out by the mobile device furtherinclude replacing a present version of the eUICC level file with adefault stored eUICC level file in response to receipt of a command todisable one or more eSIMs of the eUICC after which no eSIMs will beenabled on the eUICC.

The various aspects, embodiments, implementations or features of thedescribed embodiments can be used separately or in any combination.Various aspects of the described embodiments can be implemented bysoftware, hardware or a combination of hardware and software. Thedescribed embodiments can also be embodied as computer readable code ona computer readable medium. The computer readable medium is any datastorage device that can store data, which can thereafter be read by acomputer system. Examples of the computer readable medium includeread-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape,hard disk drives, solid state drives, and optical data storage devices.The computer readable medium can also be distributed overnetwork-coupled computer systems so that the computer readable code isstored and executed in a distributed fashion.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the describedembodiments. However, it will be apparent to one skilled in the art thatthe specific details are not required in order to practice the describedembodiments. Thus, the foregoing descriptions of specific embodimentsare presented for purposes of illustration and description. They are notintended to be exhaustive or to limit the described embodiments to theprecise forms disclosed. It will be apparent to one of ordinary skill inthe art that many modifications and variations are possible in view ofthe above teachings.

1. (canceled)
 2. A method to adapt usage of an embedded UniversalIntegrated Circuit Card (eUICC) level file on an eUICC based on anelectronic Subscriber Identity Module (eSIM) status, the methodcomprising: by the eUICC: using a default version of the eUICC levelfile when no eSIMs are enabled on the eUICC; and using a firstcustomized version of the eUICC level file when a first eSIM is enabledon the eUICC, wherein: the first customized version of the eUICC levelfile is based on first Mobile Network Operator (MNO) specificinformation applicable to the eUICC level file and included in the firsteSIM, and the default version of the eUICC level file and the firstcustomized version of the eUICC level file are both stored in a memoryof the eUICC.
 3. The method of claim 2, further comprising: by theeUICC, prior to using the first customized version of the eUICC levelfile: receiving the first eSIM; parsing the first eSIM to identify thefirst MNO specific information; and creating the first customizedversion of the eUICC level file based at least in part on the identifiedfirst MNO specific information.
 4. The method of claim 2, furthercomprising: by the eUICC: receiving a second eSIM; parsing the secondeSIM to identify second MNO specific information; creating a secondcustomized version of the eUICC level file based at least in part on theidentified second MNO specific information; and storing the secondcustomized version of the eUICC level file on the memory of the eUICC.5. The method of claim 3, further comprising: by the eUICC: using thesecond customized version of the eUICC level file when the second eSIMis enabled on the eUICC and the first eSIM is disabled on the eUICC. 6.The method of claim 2, wherein the eUICC level file comprises anelementary file (EF).
 7. The method of claim 2, wherein the eUICC levelfile specifies a hardware-specific operating parameter for the eUICC. 8.The method of claim 2, wherein the eUICC level file specifies aparameter for the eUICC for an environment class.
 9. The method of claim2, wherein the eUICC level file specific a UICC maximum powerconsumption (UMPC).
 10. The method of claim 2, wherein the eUICC storesa customized version of the eUICC level file for each eSIM stored on theeUICC.
 11. The method of claim 10, wherein the eUICC switches betweenusing different customized versions of the eUICC level file based onwhich eSIM on the eUICC is enabled.
 12. An embedded Universal IntegratedCircuit Card (eUICC) configurable for operation in a wireless device,the eUICC comprising: a memory; and a processor communicatively coupledto the memory and configured to cause the eUICC to perform actionsincluding: using a default version of an eUICC level file when noelectronic Subscriber Identity Modules (eSIMs) are enabled on the eUICC;and using a first customized version of the eUICC level file when afirst eSIM is enabled on the eUICC, wherein: the first customizedversion of the eUICC level file is based on first Mobile NetworkOperator (MNO) specific information applicable to the eUICC level fileand included in the first eSIM, and the default version of the eUICClevel file and the first customized version of the eUICC level file areboth stored in a memory of the eUICC.
 13. The eUICC of claim 12, whereinthe actions performed by the eUICC further comprise: prior to using thefirst customized version of the eUICC level file: receiving the firsteSIM; parsing the first eSIM to identify the first MNO specificinformation; and creating the first customized version of the eUICClevel file based at least in part on the identified first MNO specificinformation.
 14. The eUICC of claim 12, wherein the actions performed bythe eUICC further comprise: receiving a second eSIM; parsing the secondeSIM to identify second MNO specific information; creating a secondcustomized version of the eUICC level file based at least in part on theidentified second MNO specific information; and storing the secondcustomized version of the eUICC level file on the memory of the eUICC.15. The eUICC of claim 13, wherein the actions performed by the eUICCfurther comprise: using the second customized version of the eUICC levelfile when the second eSIM is enabled on the eUICC and the first eSIM isdisabled on the eUICC.
 16. The eUICC of claim 12, wherein the eUICClevel file specifies a hardware-specific operating parameter for theeUICC.
 17. The eUICC of claim 12, wherein the eUICC level file specifiesa parameter for the eUICC for an environment class.
 18. The eUICC ofclaim 12, wherein the eUICC level file specific a UICC maximum powerconsumption (UMPC).
 19. The eUICC of claim 12, wherein the eUICC storesa customized version of the eUICC level file for each eSIM stored on theeUICC.
 20. The eUICC of claim 19, wherein the eUICC switches betweenusing different customized versions of the eUICC level file based onwhich eSIM on the eUICC is enabled.
 21. A wireless device comprising: awireless transceiver; and an embedded Universal Integrated Circuit Card(eUICC) communicatively coupled to the wireless transceiver andconfigured to perform actions including: using a default version of aneUICC level file when no electronic Subscriber Identity Modules (eSIMs)are enabled on the eUICC; and using a first customized version of theeUICC level file when a first eSIM is enabled on the eUICC, wherein: thefirst customized version of the eUICC level file is based on firstMobile Network Operator (MNO) specific information applicable to theeUICC level file and included in the first eSIM, and the default versionof the eUICC level file and the first customized version of the eUICClevel file are both stored in a memory of the eUICC.